NTISthis.com

Evidence Guide: ICAPRG520A - Validate an application design against specifications

Student: __________________________________________________

Signature: _________________________________________________

Tips for gathering evidence to demonstrate your skills

The important thing to remember when gathering evidence is that the more evidence the better - that is, the more evidence you gather to demonstrate your skills, the more confident an assessor can be that you have learned the skills not just at one point in time, but are continuing to apply and develop those skills (as opposed to just learning for the test!). Furthermore, one piece of evidence that you collect will not usualy demonstrate all the required criteria for a unit of competency, whereas multiple overlapping pieces of evidence will usually do the trick!

From the Wiki University

 

ICAPRG520A - Validate an application design against specifications

What evidence can you provide to prove your understanding of each of the following citeria?

Evaluate software-requirement specification

  1. Review software requirement specifications document to ensure that requirements are completely specified and correct before software design begins
  2. Validate the software requirement specifications document
Review software requirement specifications document to ensure that requirements are completely specified and correct before software design begins

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Validate the software requirement specifications document

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Create a proof-of-concept prototype

  1. Use rapid application development tools to create prototype system
  2. Present prototype system for demonstration to appropriate person
  3. Validate proof of concept
Use rapid application development tools to create prototype system

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Present prototype system for demonstration to appropriate person

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Validate proof of concept

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Evaluate software design

  1. Determine if the design is complete, accurate, consistent and feasible
  2. Validate software design document
  3. Validate database structure and elements
  4. Validate user interface (UI)
  5. Review software risk analysis
Determine if the design is complete, accurate, consistent and feasible

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Validate software design document

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Validate database structure and elements

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Validate user interface (UI)

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Review software risk analysis

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Evaluate source code

  1. Validate consistency between code and software design document
  2. Validate logical structure and syntax using static analysis tools
Validate consistency between code and software design document

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Validate logical structure and syntax using static analysis tools

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Evaluate testing requirements

  1. Review and validate test plans
  2. Review and validate test cases
Review and validate test plans

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Review and validate test cases

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Document validation

  1. Document results of validation exercise
  2. Recommend current software design or itemise required alterations
  3. Submit report to appropriate person for action
Document results of validation exercise

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Recommend current software design or itemise required alterations

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Submit report to appropriate person for action

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Assessed

Teacher: ___________________________________ Date: _________

Signature: ________________________________________________

Comments:

 

 

 

 

 

 

 

 

Instructions to Assessors

Evidence Guide

The evidence guide provides advice on assessment and must be read in conjunction with the performance criteria, required skills and knowledge, range statement and the Assessment Guidelines for the Training Package.

Overview of assessment

Critical aspects for assessment and evidence required to demonstrate competency in this unit

Evidence of the ability to:

verify and validate software application design, including:

creating proof of concept (PoC) prototype

evaluating the technical specification and comparing against the PoC

interpreting and evaluating software design documentation requirements and confirming details with the client

analysing and validating user interface and database requirements

effectively using static analysis tools

walkthrough documents, test plans and test cases.

Context of and specific resources for assessment

Assessment must ensure access to:

tools to create prototype systems

static analysis tools

test plan and test cases

appropriate learning and assessment support when required

modified equipment for people with special needs.

Method of assessment

A range of assessment methods should be used to assess practical skills and knowledge. The following examples are appropriate for this unit:

review of candidate’s validation documents

evaluation of validation documents.

Guidance information for assessment

Holistic assessment with other units relevant to the industry sector, workplace and job role is recommended, where appropriate.

Assessment processes and techniques must be culturally appropriate, and suitable to the communication skill level, language, literacy and numeracy capacity of the candidate and the work being performed.

Indigenous people and other people from a non-English speaking background may need additional support.

In cases where practical assessment is used it should be combined with targeted questioning to assess required knowledge.

Required Skills and Knowledge

Required skills

analytical skills to determine audience needs

communication skills to:

interact with developer to ensure proper implementation

provide leadership and motivation

literacy skills to:

create technical documentation related to software design

read and interpret complex technical and non-technical information from a range of sources

technical skills to use:

software design tools, such as unified modelling language (UML) tools

word-processing software

UI design.

Required knowledge

basic knowledge of database design and implementation

business and technical modelling using UML tools at intermediate level

current software development methodologies

detailed knowledge of system development life cycle (SDLC)

object-oriented programming

open-source development tools

organisational procedures for documenting technical specifications

software-testing techniques.

Range Statement

The range statement relates to the unit of competency as a whole. It allows for different work environments and situations that may affect performance. Bold italicised wording, if used in the performance criteria, is detailed below. Essential operating conditions that may be present with training and assessment (depending on the work situation, needs of the candidate, accessibility of the item, and local industry and regional contexts) may also be included.

Software requirement specifications document may include:

reports

risks and resourcing

software functions

software system inputs and outputs

timeframe.

Software design document may include:

module test plan generation

test-design generation

traceability analysis

update software risk analysis.

Database structure and elements may include:

database consistency

database integrity

database structure.

User interface may include:

appearance

consistency

design

functions

navigation.

Static analysis tools may include:

Blast (c language)

Checkstyle (for Java)

JSLint (JavaScript checker)

StyleCop (for .net languages).